Skip to content

refactor(rpc): make BlockRange.block_to required#2056

Merged
kkovaacs merged 3 commits intonextfrom
krisztian/rpc-make-block-range-end-required
May 7, 2026
Merged

refactor(rpc): make BlockRange.block_to required#2056
kkovaacs merged 3 commits intonextfrom
krisztian/rpc-make-block-range-end-required

Conversation

@kkovaacs
Copy link
Copy Markdown
Contributor

@kkovaacs kkovaacs commented May 6, 2026

As part of the RPC API lock-in clients are now expected to either query the status of the node or sync the chain with SyncChainMmr before making other sync queries.

This means that the chain tip will always be known to the client when making requests containing BlockRange so we can make block_to required.

kkovaacs added 2 commits May 6, 2026 11:10
Clients are now expected to either query the status of the node or sync
the chain with `SyncChainMmr` before making other sync queries.

This means that the chain tip will always be known to the client when
making requests containing `BlockRange` so we can make `block_to` required.
@kkovaacs kkovaacs marked this pull request as ready for review May 6, 2026 09:36
Copy link
Copy Markdown
Collaborator

@Mirko-von-Leipzig Mirko-von-Leipzig left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just the comment fixup

Comment thread proto/proto/rpc.proto Outdated
Comment thread bin/stress-test/src/store/mod.rs
@kkovaacs kkovaacs merged commit 25da5ba into next May 7, 2026
17 checks passed
@kkovaacs kkovaacs deleted the krisztian/rpc-make-block-range-end-required branch May 7, 2026 12:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants